Support for using properties/getters for label creation #14
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to issue #3.
I added support for using properties/getters for label creation when using the ParamConverter from the SensioFrameworkExtraBundle. In your routing file you can define which property or getter method to use.
Use the ParamConverter in your controller to get the entity:
In your routing.yml define which property/getter to use in the breadcrumb labels:
This will get the user entity from the request (which Sensio's ParamConverter has converted from an id to an entity). It will check if the entity has a public property fullName. If not, it will try to use the public getter method getFullName(). If that also fails, it will try to use the entity's __toString() magic fuction.